Restarting Order Management System

Purpose: It is necessary to restart Order Management System in order for certain changes to take effect; see Restarting the Order Management System Application Servers.

When Cloud administration staff restart Order Management System Cloud Service, the system also looks at settings in Working with Admin Properties (CPRP) to determine the periodic process and its assigned periodic functions to run once Order Management System Cloud Service has restarted; see Running a Periodic Process on Server Startup.

Before restarting: Notify all users before restarting Order Management System Cloud Service, as restarting ends all currently open sessions and stops all active jobs.

Note: If Cloud administration staff restart Order Management System Cloud Service without first stopping all active processes and completing the associated running jobs, the processes and jobs will not end normally. Any processes and jobs that did not end normally will need to be reset to inactive manually when you log back in to Order Management System Cloud Service.

Restarting the Order Management System Application Servers

Use the following steps to restart one or more of the Order Management System Cloud Service application servers.

1. Log in to the WebLogic Server Administration Console. The user ID you log in with must be part of the Administrators group.

2. On the home page, locate the Environment pane and click Clusters to advance to the Summary of Clusters page.

3. On the Summary of Clusters page, click the name of the cluster used for Order Management System to advance to the Settings for Cluster page.

4. On the Settings for Cluster page, click the Control tab to display the application servers for Order Management System. The State of the server indicates whether the application is currently running.

To stop one or more application servers that is currently running:

- Select the check box next to the server and click Shutdown > Force Shutdown Now. At the confirmation window, click Yes to shut down the server.

- Refresh the screen until the State of the server is SHUTDOWN and the Status of Last Action is TASK COMPLETED.

To start one or more application servers that is currently shutdown:

- Select the check box next to the server and click Start. At the confirmation window, click Yes to start the server.

- Refresh the screen until the State of the server is RUNNING and the Status of Last Action is TASK COMPLETED.

Running a Periodic Process on Server Startup

When Cloud administration staff restart Order Management System Cloud Service (see Restarting Order Management System), the system looks at the settings in Working with Admin Properties (CPRP) to determine the periodic process and its assigned periodic functions to run on server startup.

Why run a periodic process at startup? Typically, you would assign the periodic functions that start the async, e-commerce, integration layer jobs, and Drop Ship Background job to the periodic process that starts on server startup. However, you can assign any periodic function to the periodic process that runs on server startup. You can use the Work with Process Assignments Screen (Assigning Functions to a Periodic Process) in Working with Periodic Processes (WPPR) to assign periodic functions to the periodic process and select which of these periodic functions will run the next time you restart Order Management System Cloud Service. See Periodic Functions Available to Schedule for a list of periodic functions available to assign to the periodic process that is scheduled to run on server startup.

Required properties file setting: Periodic processes can run at server startup only if CWDIRECTCP_ALLOW_ SCHEDULING_ON_THIS_SERVER in the CWDirectCP Server Properties File is selected. Typically, Cloud admin staff would select this setting in the properties file on a single server.

Scheduled jobs: When Order Management System Cloud Service executes the specified periodic process at server startup, the system schedules the periodic process to run one time. You can review the periodic process on the Scheduled Jobs Screen. The user assigned to the periodic process is the user ID defined in the STARTUP_ USER_TO _RUN_ PERIODIC _PROCESS monitor property setting. Any jobs submitted by the periodic functions assigned to the periodic process display on the My Jobs screen under this user ID. See Scheduling Jobs for more information on scheduled jobs.

Note: If you have scheduled the periodic process to run on server startup, do not define a job schedule for this periodic process. Instead, create one periodic process to run on server startup and a separate periodic process to schedule for other times. See Defining the Job Schedule for more information on setting up a schedule for a periodic process.

Application log: The system writes a message to the Application Log if its Logging Level is set to INFO and you do not set up the monitor properties correctly; for example: StartUpPeriodicProcess failed to start because Scheduling is not allowed on this server. If an error occurs, you need to correct the error and stop and restart Order Management System Cloud Service.

Monitor Property Settings

The Monitor Properties in Working with Admin Properties (CPRP) contain the settings required to have the system run a specified periodic process and its assigned periodic functions when you restart Order Management System Cloud Service.

Property Name	Description
STARTUP_ PERIODIC_ PROCESS_TO_RUN	The name of the periodic process to run when you restart Order Management System Cloud Service. The process you enter must be a valid periodic process with assigned periodic functions. See Working with Periodic Processes (WPPR) for more information on creating a periodic process and how to assign periodic functions to it.
STARTUP_NBR_MINUTES_TO_WAIT_ BEFORE_ RUNNING_ PERIODIC_ PROCESS	The number of minutes after system startup that the periodic process should be scheduled to start. This time allows Order Management System Cloud Service to start up completely before running the periodic process. Valid values are 1-999 minutes. The delivered setting is 5 minutes. Required if a periodic process is defined in the STARTUP_PERIODIC_PROCESS_TO_RUN setting.
STARTUP_ USER_TO _RUN_ PERIODIC _PROCESS	The user ID to run the periodic process; enter the user ID in all caps, for example JSMITH and not jsmith. This is the user ID that displays on the Scheduled Jobs Screen for the periodic process; any jobs submitted for the periodic process are also assigned to this user ID. This must be a valid user ID in the User table. Required if a periodic process is defined in the STARTUP_PERIODIC_PROCESS_TO_RUN setting.
STARTUP_ COMPANY_TO_RUN_ PERIODIC_ PROCESS	The company number used to run a periodic function that requires a company to be defined. If none of the periodic functions require a company number, enter your default company number or 1. Valid values are 1-999. The system does not validate that your entry is a valid company number. Required if a periodic process is defined in the STARTUP_PERIODIC_PROCESS_TO_RUN setting.

For more information: See Long Running Jobs Monitor for more information on the settings in the Monitor Properties file related to the Long Running Jobs Monitor.